Collision resolution

• Add resolveCollisions option to .typeSchema() for explicit control over duplicate schema selection
  • Key: binding URL (e.g. urn:fhir:binding:ObservationCategory), value: { package, canonical } identifying the preferred source
  • Unresolved collisions keep current behavior (pick most common, warn #duplicateSchema)
  • Mismatched config emits #resolveCollisionMiss warning
• IR report enhancements:
  • Version marks: (selected) for user-configured, (auto) for heuristic-picked
  • Suggested resolveCollisions config snippet for unresolved collisions

Config example:

.typeSchema({
    resolveCollisions: {
        "urn:fhir:binding:ObservationCategory": {
            package: "hl7.fhir.r4.core#4.0.1",
            canonical: "http://hl7.org/fhir/StructureDefinition/Observation",
        },
    },
})

Generated report example:

## Schema Collisions

- `urn:fhir:binding:CommunicationReason` (2 versions)
  - Version 1 (selected): Communication (hl7.fhir.r4.core#4.0.1)
  - Version 2: CommunicationRequest (hl7.fhir.r4.core#4.0.1)
- `urn:fhir:binding:ProcessPriority` (2 versions)
  - Version 1 (auto): Claim (hl7.fhir.r4.core#4.0.1), CoverageEligibilityRequest (hl7.fhir.r4.core#4.0.1)
  - Version 2: ExplanationOfBenefit (hl7.fhir.r4.core#4.0.1)

### Suggested `resolveCollisions` config

.typeSchema({
    resolveCollisions: {
        "urn:fhir:binding:ProcessPriority": {
            package: "hl7.fhir.r4.core#4.0.1",
            canonical: "http://hl7.org/fhir/StructureDefinition/Claim",
        },
    },
})

Refactoring

• Group treeShake, promoteLogical, resolveCollisions under options.typeSchema?: IrConf in APIBuilderOptions

Documentation

• Add "Resolving Schema Collisions" section to README with warning explanation, fix instructions, and report output example
• Update CLAUDE.md and README APIBuilder flow examples